Conversation
️✔️AzureCLI-FullTest
|
azure-client-tools-bot-prd
bot
added this to the
Build 2025 (2025-05-19)❗ Breaking change release ❗ milestone
️✔️AzureCLI-BreakingChangeTest
|
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
Collaborator
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
microsoft-github-policy-service
bot
added
Auto-Assign
mohitagarwal-sql
changed the title
emgu-ms
approved these changes
Apr 25, 2025
evelyn-ys
approved these changes
Apr 29, 2025
evelyn-ys
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related command
az sql db update -g $resourceGroupName -s $serverName -n $databaseName --edition Hyperscale --service-objective $serviceObjective --no-waitaz sql db update -g $resourceGroupName -s $serverName -n $databaseName --elastic-pool $hyperscaleElasticPool --no-waitDescription
When initiating an Update-SLO from the Sterling tier (GeneralPurpose/BusinessCritical/Basic/Standard/Premium ) in SQL DB to the Hyperscale tier for a database that has a geo-replication link, this PR introduces a warning message to inform the Customer about the process. The warning message will be displayed at the start of the update operation, ensuring that the Customer is aware of the implications and necessary steps involved in the transition to the Hyperscale tier.
Testing Guide
Create database:
az sql db create -g $resourceGroupName -s $serverName -n $databaseName --edition GeneralPurpose --service-objective GP_Gen5_2Create geo-replicated database:
az sql db replica create --name $database --resource-group $resourceGroup --server $server --partner-server $secondaryServer --partner-resource-group $resourceGroup --partner-database $databaseUpdate SLO to Hyperscale tier using one of the below commands:
az sql db update -g $resourceGroupName -s $serverName -n $databaseName --service-objective $serviceObjective --no-waitaz sql db update -g $resourceGroupName -s $serverName -n $databaseName --edition Hyperscale --no-waitaz sql db update -g $resourceGroupName -s $serverName -n $databaseName --elastic-pool $hyperscaleElasticPool --no-waitHistory Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.